Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 003109a2e8f5753e4b0dde934872ff941a03ec1140e9cfee3b764e5bfad086d7

Tx prefix hash: 6cf30d797f32e748101486b60a00e70b816e42f3cf7f59f464303cbb6702f658
Tx public key: c58b8cacd3fc8eb372219ca8f3697b1436b8a93174f5e237006d4f70bf69492d
Timestamp: 1704369723 Timestamp [UCT]: 2024-01-04 12:02:03 Age [y:d:h:m:s]: 01:171:02:58:24
Block: 927982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383213 RingCT/type: yes/0
Extra: 01c58b8cacd3fc8eb372219ca8f3697b1436b8a93174f5e237006d4f70bf69492d021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23e4a259aba3bd27b0bf01bee958359581a2aa1ea4627efb73a79713e793e032 0.600000000000 1385830 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": 927992, "vin": [ { "gen": { "height": 927982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23e4a259aba3bd27b0bf01bee958359581a2aa1ea4627efb73a79713e793e032" } } ], "extra": [ 1, 197, 139, 140, 172, 211, 252, 142, 179, 114, 33, 156, 168, 243, 105, 123, 20, 54, 184, 169, 49, 116, 245, 226, 55, 0, 109, 79, 112, 191, 105, 73, 45, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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