Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 481ce7974ac993b7ccdf884037c3d7fca0bcd83bc224afdf8710c2bf28deee25

Tx prefix hash: 849661047bcb04d5632ce05b1cdfa37c8a88ce33103f923e431e9fb9a0e615a2
Tx public key: 698eeefc3549fb0ae11a15538cbfc0dd4aae29dab23e1d0d5970dcfcfff95325
Timestamp: 1735806061 Timestamp [UCT]: 2025-01-02 08:21:01 Age [y:d:h:m:s]: 00:168:09:03:10
Block: 1188467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120038 RingCT/type: yes/0
Extra: 01698eeefc3549fb0ae11a15538cbfc0dd4aae29dab23e1d0d5970dcfcfff95325021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d244e5b9b30d2ffd6d03ba06d52bbdd9b17e67ee37978c23600aa0ba7978312e 0.600000000000 1674968 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": 1188477, "vin": [ { "gen": { "height": 1188467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d244e5b9b30d2ffd6d03ba06d52bbdd9b17e67ee37978c23600aa0ba7978312e" } } ], "extra": [ 1, 105, 142, 238, 252, 53, 73, 251, 10, 225, 26, 21, 83, 140, 191, 192, 221, 74, 174, 41, 218, 178, 62, 29, 13, 89, 112, 220, 252, 255, 249, 83, 37, 2, 17, 0, 0, 0, 2, 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