Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ce5d8908880736e445f66b560083e717e1ebb00a4e4be3cb83e882a6f3b816b

Tx prefix hash: 8745bbb6e83a63b077fd700139ea44b8439ccf28bec09dbf0f21cfe78991bae1
Tx public key: 278ad9c0c84c14a3c420bf0b17bca84595d899056d34cf86d54ba730e0344653
Timestamp: 1754928947 Timestamp [UCT]: 2025-08-11 16:15:47 Age [y:d:h:m:s]: 00:053:02:51:41
Block: 1344922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37141 RingCT/type: yes/0
Extra: 01278ad9c0c84c14a3c420bf0b17bca84595d899056d34cf86d54ba730e0344653021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f278fb5e0c14d91aaf45d04e7687f550c53943a1d87e738868a1a1a24d0b3be0 0.600000000000 1832809 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": 1344932, "vin": [ { "gen": { "height": 1344922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f278fb5e0c14d91aaf45d04e7687f550c53943a1d87e738868a1a1a24d0b3be0" } } ], "extra": [ 1, 39, 138, 217, 192, 200, 76, 20, 163, 196, 32, 191, 11, 23, 188, 168, 69, 149, 216, 153, 5, 109, 52, 207, 134, 213, 75, 167, 48, 224, 52, 70, 83, 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