Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1809d46564718469a02d12c8843aed74349e2f56a572c735f29947674b33bc5b

Tx prefix hash: eed46e8b895e6566b8c6d07eeb27e552a1dc325b9db8338027241ee4fb13b2a5
Tx public key: db926632e7b1e9a26320fd7d8f4df935bfdeaa15f2a3a335c09dc5f477193a90
Timestamp: 1705631529 Timestamp [UCT]: 2024-01-19 02:32:09 Age [y:d:h:m:s]: 01:351:07:22:55
Block: 938404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 509994 RingCT/type: yes/0
Extra: 01db926632e7b1e9a26320fd7d8f4df935bfdeaa15f2a3a335c09dc5f477193a90

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7ca9424a08abca292bb582767a80b84945e6d331d5294f846b647546cf3fd92 0.600000000000 1396474 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": 938414, "vin": [ { "gen": { "height": 938404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7ca9424a08abca292bb582767a80b84945e6d331d5294f846b647546cf3fd92" } } ], "extra": [ 1, 219, 146, 102, 50, 231, 177, 233, 162, 99, 32, 253, 125, 143, 77, 249, 53, 191, 222, 170, 21, 242, 163, 163, 53, 192, 157, 197, 244, 119, 25, 58, 144 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8