Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2f93a07dbd7eea1686c6a8020e83fc1ed2c3bc66618119567b0f9b13e0e25b5

Tx prefix hash: 73317b4aad1a0bb3e874f77c16389677b2d69c0ec94f199c88c3151ed52c735f
Tx public key: da0b748ce87a6e3b510ad55c7f6ef4aec99b8234d35adcbf24a417d25c8fd3f8
Timestamp: 1731777492 Timestamp [UCT]: 2024-11-16 17:18:12 Age [y:d:h:m:s]: 00:136:07:56:42
Block: 1155089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97261 RingCT/type: yes/0
Extra: 01da0b748ce87a6e3b510ad55c7f6ef4aec99b8234d35adcbf24a417d25c8fd3f802110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d05582bc6404fbadf3eae5bcf87cd15a91f57010d2f5271ff9a8c1be17d0e5ba 0.600000000000 1640704 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": 1155099, "vin": [ { "gen": { "height": 1155089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d05582bc6404fbadf3eae5bcf87cd15a91f57010d2f5271ff9a8c1be17d0e5ba" } } ], "extra": [ 1, 218, 11, 116, 140, 232, 122, 110, 59, 81, 10, 213, 92, 127, 110, 244, 174, 201, 155, 130, 52, 211, 90, 220, 191, 36, 164, 23, 210, 92, 143, 211, 248, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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