Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a304a02d56688cbca06bad4a8ee905c5a5c5ec410c4344cd7708fd81365613c3

Tx prefix hash: 367b8f511b141c604452d7a4978bd75115f1db81549239d916c1d27d179a3d90
Tx public key: 255fe7bc877ba1313a5d4284d496a80548c8d65a0838beb5d7e281d2fed5b6ca
Timestamp: 1717079354 Timestamp [UCT]: 2024-05-30 14:29:14 Age [y:d:h:m:s]: 00:314:13:52:25
Block: 1033343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224833 RingCT/type: yes/0
Extra: 01255fe7bc877ba1313a5d4284d496a80548c8d65a0838beb5d7e281d2fed5b6ca0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 141a17a9aafa6ab81d069c891834612a31906823ea62883b7fff9fcd2ab0b92d 0.600000000000 1501808 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": 1033353, "vin": [ { "gen": { "height": 1033343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "141a17a9aafa6ab81d069c891834612a31906823ea62883b7fff9fcd2ab0b92d" } } ], "extra": [ 1, 37, 95, 231, 188, 135, 123, 161, 49, 58, 93, 66, 132, 212, 150, 168, 5, 72, 200, 214, 90, 8, 56, 190, 181, 215, 226, 129, 210, 254, 213, 182, 202, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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