Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 64369c99954bf97360769074f37e33c7166c812525ed6f548de2fd0f42bc6bd4

Tx prefix hash: 5199ab30197c18a1ee792ded3b7414f7d955c6317a63a035b4076d15ebdd73b9
Tx public key: 38baf656a9f2243e8af0b3d1f3b7a1aa3f13d5df00ab7ef916eae163284dddde
Timestamp: 1595255656 Timestamp [UCT]: 2020-07-20 14:34:16 Age [y:d:h:m:s]: 05:107:15:24:48
Block: 118672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1285920 RingCT/type: yes/0
Extra: 0138baf656a9f2243e8af0b3d1f3b7a1aa3f13d5df00ab7ef916eae163284dddde0211000000044943cd9f000000000000000000

1 output(s) for total of 248.193918773000 dcy

stealth address amount amount idx
00: 03dd33fa363f7a291667b695debe0fabf10f86b42e67478949f898f399e32e54 248.193918773000 202530 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 118682, "vin": [ { "gen": { "height": 118672 } } ], "vout": [ { "amount": 248193918773, "target": { "key": "03dd33fa363f7a291667b695debe0fabf10f86b42e67478949f898f399e32e54" } } ], "extra": [ 1, 56, 186, 246, 86, 169, 242, 36, 62, 138, 240, 179, 209, 243, 183, 161, 170, 63, 19, 213, 223, 0, 171, 126, 249, 22, 234, 225, 99, 40, 77, 221, 222, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8