Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 481f7d76c3c49b4513a31749c23545a47eccffd7b94da6ea6cc18397ddf381ab

Tx prefix hash: e51a1a328020722f11876fb213b4ef1ee2c29735656922afc26a5b0f166ae73a
Tx public key: 42b6df8b93daddb9338e5cd905cc8afe7b47eaa14892cc3d3fcc62d27c84d612
Timestamp: 1712706890 Timestamp [UCT]: 2024-04-09 23:54:50 Age [y:d:h:m:s]: 01:207:23:52:37
Block: 997071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407326 RingCT/type: yes/0
Extra: 0142b6df8b93daddb9338e5cd905cc8afe7b47eaa14892cc3d3fcc62d27c84d6120211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7e53cf969da2d2be55bc83c5178d389eccc84a84eca692e849ba580c8d7eace 0.600000000000 1457499 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": 997081, "vin": [ { "gen": { "height": 997071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7e53cf969da2d2be55bc83c5178d389eccc84a84eca692e849ba580c8d7eace" } } ], "extra": [ 1, 66, 182, 223, 139, 147, 218, 221, 185, 51, 142, 92, 217, 5, 204, 138, 254, 123, 71, 234, 161, 72, 146, 204, 61, 63, 204, 98, 210, 124, 132, 214, 18, 2, 17, 0, 0, 0, 3, 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