Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac0b4bc36a2cd1809c92774a25f16756d92e147694c321406f340e05367a1424

Tx prefix hash: 924c0593ac4e6e1a38a6060b2362059f4bcb09c366b4baf237bc681b91731969
Tx public key: cb5d1148766337826d76e8d5377598886947c458e8266d6537b0200109020a3e
Timestamp: 1694232269 Timestamp [UCT]: 2023-09-09 04:04:29 Age [y:d:h:m:s]: 02:119:21:54:11
Block: 844113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 605473 RingCT/type: yes/0
Extra: 01cb5d1148766337826d76e8d5377598886947c458e8266d6537b0200109020a3e021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.979722965000 dcy

stealth address amount amount idx
00: cbae9c7e9f71dd9f416890f8b20e5ead0e003c4cbdafd6128a3a2b0ac66cf112 0.979722965000 1297401 of 0

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": 844123, "vin": [ { "gen": { "height": 844113 } } ], "vout": [ { "amount": 979722965, "target": { "key": "cbae9c7e9f71dd9f416890f8b20e5ead0e003c4cbdafd6128a3a2b0ac66cf112" } } ], "extra": [ 1, 203, 93, 17, 72, 118, 99, 55, 130, 109, 118, 232, 213, 55, 117, 152, 136, 105, 71, 196, 88, 232, 38, 109, 101, 55, 176, 32, 1, 9, 2, 10, 62, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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