Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 527292df9324a6507e772636717c984be529842306e257526ee99990696b5165

Tx prefix hash: 5a8af1f69181744bdd1cffb6777c85b49e31ede9e7ca6cc1f49479299b0ceb24
Tx public key: 6e97e3e2aa6cc50e6e794e3c88dceb0a18b6300c4c29d9928641d7aa8436a67e
Timestamp: 1754662687 Timestamp [UCT]: 2025-08-08 14:18:07 Age [y:d:h:m:s]: 00:096:19:08:09
Block: 1342868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68271 RingCT/type: yes/0
Extra: 016e97e3e2aa6cc50e6e794e3c88dceb0a18b6300c4c29d9928641d7aa8436a67e021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b871f9b7d0f1f1e9a0c29c5cd8db037a1c5384590a987e4c3cb0ccfc6e22867a 0.600000000000 1830701 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": 1342878, "vin": [ { "gen": { "height": 1342868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b871f9b7d0f1f1e9a0c29c5cd8db037a1c5384590a987e4c3cb0ccfc6e22867a" } } ], "extra": [ 1, 110, 151, 227, 226, 170, 108, 197, 14, 110, 121, 78, 60, 136, 220, 235, 10, 24, 182, 48, 12, 76, 41, 217, 146, 134, 65, 215, 170, 132, 54, 166, 126, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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