Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa46e36aa8d31050ea759448a73d137bfd6dd3a08be04e6fdfde8f4e3f88fb12

Tx prefix hash: 6b5d04745e03c555ce8fe9a20725353a6ffee4885b0a46cdf827db174d196ab7
Tx public key: 5c89f257ceb51f06c207e4ba4f061c7608cc308118698473b340b4616875eeb4
Timestamp: 1719634116 Timestamp [UCT]: 2024-06-29 04:08:36 Age [y:d:h:m:s]: 00:267:00:18:32
Block: 1054520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190793 RingCT/type: yes/0
Extra: 015c89f257ceb51f06c207e4ba4f061c7608cc308118698473b340b4616875eeb40211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 392b866dcfde9eba01b4e6c33de55816a80165867eea37dbd9e3de40d2e26225 0.600000000000 1524883 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": 1054530, "vin": [ { "gen": { "height": 1054520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "392b866dcfde9eba01b4e6c33de55816a80165867eea37dbd9e3de40d2e26225" } } ], "extra": [ 1, 92, 137, 242, 87, 206, 181, 31, 6, 194, 7, 228, 186, 79, 6, 28, 118, 8, 204, 48, 129, 24, 105, 132, 115, 179, 64, 180, 97, 104, 117, 238, 180, 2, 17, 0, 0, 0, 2, 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