Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59a8ebdcc48cc5ee4bb1516ab417f4b2cf7feee0c40a1e2224e5b00302940059

Tx prefix hash: 11c81b7cf803b51a6de7d740774c8862bfe167d742515b45a7cfb6c70330ee4c
Tx public key: d3074e43c53bf915a626e5ee8a70fb4aa54dbfbadd49b8ec68c56995853299fe
Timestamp: 1720790217 Timestamp [UCT]: 2024-07-12 13:16:57 Age [y:d:h:m:s]: 00:247:16:47:07
Block: 1064117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176959 RingCT/type: yes/0
Extra: 01d3074e43c53bf915a626e5ee8a70fb4aa54dbfbadd49b8ec68c56995853299fe02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bbb16138ee649508af7b5ced187e90aa662b76645a6f234cfdf1d1d49161dd8 0.600000000000 1534640 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": 1064127, "vin": [ { "gen": { "height": 1064117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bbb16138ee649508af7b5ced187e90aa662b76645a6f234cfdf1d1d49161dd8" } } ], "extra": [ 1, 211, 7, 78, 67, 197, 59, 249, 21, 166, 38, 229, 238, 138, 112, 251, 74, 165, 77, 191, 186, 221, 73, 184, 236, 104, 197, 105, 149, 133, 50, 153, 254, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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