Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e92a47aa981fb8a16afce62e1f9c05187964e9380d2ccb32f4105b9b16556632

Tx prefix hash: bda53cf6abdf97bc087084f065e202eb4e07706c3dc245c1b93ac7bca2cccbca
Tx public key: 839070c945350713f577446582f0b6ffbc7317ea4b77439f3b7419bf5eb6c131
Timestamp: 1741338129 Timestamp [UCT]: 2025-03-07 09:02:09 Age [y:d:h:m:s]: 00:309:11:26:18
Block: 1233995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219013 RingCT/type: yes/0
Extra: 01839070c945350713f577446582f0b6ffbc7317ea4b77439f3b7419bf5eb6c131021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35b9b283e87535d84f6743e5ecf239de3e7a76bb7c07b34059472dc5f78a3f58 0.600000000000 1720920 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": 1234005, "vin": [ { "gen": { "height": 1233995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35b9b283e87535d84f6743e5ecf239de3e7a76bb7c07b34059472dc5f78a3f58" } } ], "extra": [ 1, 131, 144, 112, 201, 69, 53, 7, 19, 245, 119, 68, 101, 130, 240, 182, 255, 188, 115, 23, 234, 75, 119, 67, 159, 59, 116, 25, 191, 94, 182, 193, 49, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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