Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 485ddf59e29bc198cad3912c84404c7ef85d25c19adbdf66e38ba6d4b0a0c14b

Tx prefix hash: e584339c052497fc247d936632328d6189803bf30684bb89d553f9350f4a4c50
Tx public key: 89a876d07d78299f03193dfe086b8f9c3e962f87195a46ddf0c727e2da40a953
Timestamp: 1749620428 Timestamp [UCT]: 2025-06-11 05:40:28 Age [y:d:h:m:s]: 00:157:23:59:05
Block: 1302552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110612 RingCT/type: yes/0
Extra: 0189a876d07d78299f03193dfe086b8f9c3e962f87195a46ddf0c727e2da40a953021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c56ba6a1c02a2322b1705c03e2e103feba6b52c2ce455f763451476ab5ec7fe 0.600000000000 1790123 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": 1302562, "vin": [ { "gen": { "height": 1302552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c56ba6a1c02a2322b1705c03e2e103feba6b52c2ce455f763451476ab5ec7fe" } } ], "extra": [ 1, 137, 168, 118, 208, 125, 120, 41, 159, 3, 25, 61, 254, 8, 107, 143, 156, 62, 150, 47, 135, 25, 90, 70, 221, 240, 199, 39, 226, 218, 64, 169, 83, 2, 17, 0, 0, 0, 3, 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