Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1382440e98d36bad35bfe89edea0a0c6e13bdc9ac7c8a893c5971fe65dbd65de

Tx prefix hash: e9bcf112c3eb10b951f05356c473f1ec38ef9deae4f554df6376fcd773c0afb6
Tx public key: 4ce8b55f917ed659f072f69facd40736a26843ae9c38e4e1616e7346524d1285
Timestamp: 1761871375 Timestamp [UCT]: 2025-10-31 00:42:55 Age [y:d:h:m:s]: 00:009:02:06:48
Block: 1401580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6490 RingCT/type: yes/0
Extra: 014ce8b55f917ed659f072f69facd40736a26843ae9c38e4e1616e7346524d128502110000000725a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 671a1a7cc6a2b8b916c4a0217c779deb34385313b86dc73ae36832df7f6fc2d6 0.600000000000 1889899 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": 1401590, "vin": [ { "gen": { "height": 1401580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "671a1a7cc6a2b8b916c4a0217c779deb34385313b86dc73ae36832df7f6fc2d6" } } ], "extra": [ 1, 76, 232, 181, 95, 145, 126, 214, 89, 240, 114, 246, 159, 172, 212, 7, 54, 162, 104, 67, 174, 156, 56, 228, 225, 97, 110, 115, 70, 82, 77, 18, 133, 2, 17, 0, 0, 0, 7, 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