Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd4ecfb74da733a040ecca1ff1c291f0a754aec3fc5d78adad3156de695877fa

Tx prefix hash: c51fcce747ba1d7a23810fdc6b1c756cd8dfa6d467f39f35d5a24f09948d2ed8
Tx public key: 209c28346bbab56090fd036017b596535f8ad3cd1ba1ea760fe29096dad8dbc4
Timestamp: 1648632559 Timestamp [UCT]: 2022-03-30 09:29:19 Age [y:d:h:m:s]: 03:029:05:41:35
Block: 469474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 801191 RingCT/type: yes/0
Extra: 01209c28346bbab56090fd036017b596535f8ad3cd1ba1ea760fe29096dad8dbc402110000000306faf294000000000000000000

1 output(s) for total of 17.078038973000 dcy

stealth address amount amount idx
00: 259fd8a534406381a546fbcb8ff82b73df095a1444e951aab2250fc19a1c6469 17.078038973000 888428 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": 469484, "vin": [ { "gen": { "height": 469474 } } ], "vout": [ { "amount": 17078038973, "target": { "key": "259fd8a534406381a546fbcb8ff82b73df095a1444e951aab2250fc19a1c6469" } } ], "extra": [ 1, 32, 156, 40, 52, 107, 186, 181, 96, 144, 253, 3, 96, 23, 181, 150, 83, 95, 138, 211, 205, 27, 161, 234, 118, 15, 226, 144, 150, 218, 216, 219, 196, 2, 17, 0, 0, 0, 3, 6, 250, 242, 148, 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