Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aad4ae0ee388d0229cf27cd45004d88294d4070c8609d77bb86e3b4d0e419e5

Tx prefix hash: 9d449238ba17ef6ee4c70992e8f05a3718727fdff81e28e039b8562362e8b1eb
Tx public key: 806175fb80c9d4423f0fe957058d0b280ba7cd3faf904d595a505d3c9985186b
Timestamp: 1737026499 Timestamp [UCT]: 2025-01-16 11:21:39 Age [y:d:h:m:s]: 00:155:08:03:46
Block: 1198559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110683 RingCT/type: yes/0
Extra: 01806175fb80c9d4423f0fe957058d0b280ba7cd3faf904d595a505d3c9985186b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d93873ef79e2126deaf5b6f35e834d4cfbd927237d345ba36a13fe009a16d962 0.600000000000 1685184 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": 1198569, "vin": [ { "gen": { "height": 1198559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d93873ef79e2126deaf5b6f35e834d4cfbd927237d345ba36a13fe009a16d962" } } ], "extra": [ 1, 128, 97, 117, 251, 128, 201, 212, 66, 63, 15, 233, 87, 5, 141, 11, 40, 11, 167, 205, 63, 175, 144, 77, 89, 90, 80, 93, 60, 153, 133, 24, 107, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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