Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c78ace881345e420f7435c73be18cbc7cd6d6af25e52b79a8d7692d543c619

Tx prefix hash: 6a6abbffb8c64087eda91f16cc2de9ca7b008bee0d4122eec4ad404ba70206c4
Tx public key: e8c909d7455f6e3d7cde5fa8263478d2134faf7bfca23cfddb722136f3e6bae3
Timestamp: 1750955950 Timestamp [UCT]: 2025-06-26 16:39:10 Age [y:d:h:m:s]: 00:147:21:53:49
Block: 1313290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103716 RingCT/type: yes/0
Extra: 01e8c909d7455f6e3d7cde5fa8263478d2134faf7bfca23cfddb722136f3e6bae3021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b00864d1a40ddb7ad8194e7464315e45b861cecd42d69f728e4a4b8cb325673 0.600000000000 1800929 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": 1313300, "vin": [ { "gen": { "height": 1313290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b00864d1a40ddb7ad8194e7464315e45b861cecd42d69f728e4a4b8cb325673" } } ], "extra": [ 1, 232, 201, 9, 215, 69, 95, 110, 61, 124, 222, 95, 168, 38, 52, 120, 210, 19, 79, 175, 123, 252, 162, 60, 253, 219, 114, 33, 54, 243, 230, 186, 227, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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