Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 371c7421e82034397b19cd44f0cad52f54cfca3cc7348deccccdf83b42975a5d

Tx prefix hash: 96a64780d99e3b99acd338cc707588e954f19ee396fc0ebe6f31c833f9d69887
Tx public key: 5be52206f2b89ed168edf0a1fb1b0a8a70b7e0b956eaeb79952da4a3753ba810
Timestamp: 1702660179 Timestamp [UCT]: 2023-12-15 17:09:39 Age [y:d:h:m:s]: 01:147:15:00:11
Block: 913792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366674 RingCT/type: yes/0
Extra: 015be52206f2b89ed168edf0a1fb1b0a8a70b7e0b956eaeb79952da4a3753ba81002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07e7da09b08bb904741ae14cc170790db4da1e739b48c75d1054fe705a96c8e1 0.600000000000 1371070 of 15

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": 913802, "vin": [ { "gen": { "height": 913792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07e7da09b08bb904741ae14cc170790db4da1e739b48c75d1054fe705a96c8e1" } } ], "extra": [ 1, 91, 229, 34, 6, 242, 184, 158, 209, 104, 237, 240, 161, 251, 27, 10, 138, 112, 183, 224, 185, 86, 234, 235, 121, 149, 45, 164, 163, 117, 59, 168, 16, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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