Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b891a2cd1ce4c0c04d851279b839547ac2168c8d21565af0fd39996b0853fff5

Tx prefix hash: 5ea8f74f865fee7d363e7146ca4f0e40f2f6ac5fa2c039981e8bc584a8074021
Tx public key: ed49bb7cba4a31774655cfaeb1412d3b7b5d4030cb9f33e859964ca635c35126
Timestamp: 1750979906 Timestamp [UCT]: 2025-06-26 23:18:26 Age [y:d:h:m:s]: 00:141:01:14:25
Block: 1313483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98823 RingCT/type: yes/0
Extra: 01ed49bb7cba4a31774655cfaeb1412d3b7b5d4030cb9f33e859964ca635c351260211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a0375c7690983d1551484844d8938b880917a5a98d4a310f9f75a5d984b2741 0.600000000000 1801124 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": 1313493, "vin": [ { "gen": { "height": 1313483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a0375c7690983d1551484844d8938b880917a5a98d4a310f9f75a5d984b2741" } } ], "extra": [ 1, 237, 73, 187, 124, 186, 74, 49, 119, 70, 85, 207, 174, 177, 65, 45, 59, 123, 93, 64, 48, 203, 159, 51, 232, 89, 150, 76, 166, 53, 195, 81, 38, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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