Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 902f348db2c2c055e29f3a200d387c74ffdf9cc9a3b50670a8a006b2ee8003fc

Tx prefix hash: c8a83caa82fd49207bc60e13e4ffed069ee411ec9103760b4978d1c9d3ae79e0
Tx public key: d3e9fca58f25cbfe6c8aa316b77a1efaa7e870d44ff4fe4843b30821e9bdf96d
Timestamp: 1686293017 Timestamp [UCT]: 2023-06-09 06:43:37 Age [y:d:h:m:s]: 01:303:09:04:25
Block: 778367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477995 RingCT/type: yes/0
Extra: 01d3e9fca58f25cbfe6c8aa316b77a1efaa7e870d44ff4fe4843b30821e9bdf96d02110000000133af99f4000000000000000000

1 output(s) for total of 1.617883236000 dcy

stealth address amount amount idx
00: 3341c7d0d73f3e663129d62b6f7539784f81fbbc2ac0639c39136bd6056f718c 1.617883236000 1227988 of 0

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": 778377, "vin": [ { "gen": { "height": 778367 } } ], "vout": [ { "amount": 1617883236, "target": { "key": "3341c7d0d73f3e663129d62b6f7539784f81fbbc2ac0639c39136bd6056f718c" } } ], "extra": [ 1, 211, 233, 252, 165, 143, 37, 203, 254, 108, 138, 163, 22, 183, 122, 30, 250, 167, 232, 112, 212, 79, 244, 254, 72, 67, 179, 8, 33, 233, 189, 249, 109, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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