Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be485628de7499968abab9ca96d022e514abcb32a22b292a853c5827f770ad01

Tx prefix hash: 2b10f44fef93417d6841ed75dc02b4a541edcf7c237f5d9127dfddf3b0747ea4
Tx public key: 875af06faac6fa2eede25958d9c3953bd6c10f0ee905367ba3cee63e7c87b476
Timestamp: 1735312934 Timestamp [UCT]: 2024-12-27 15:22:14 Age [y:d:h:m:s]: 00:097:11:04:36
Block: 1184375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69440 RingCT/type: yes/0
Extra: 01875af06faac6fa2eede25958d9c3953bd6c10f0ee905367ba3cee63e7c87b476021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 079417c0f4d28b3c4f0dd7c201603d1801d35569e7fa38d123dc2e23b619017e 0.600000000000 1670832 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": 1184385, "vin": [ { "gen": { "height": 1184375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "079417c0f4d28b3c4f0dd7c201603d1801d35569e7fa38d123dc2e23b619017e" } } ], "extra": [ 1, 135, 90, 240, 111, 170, 198, 250, 46, 237, 226, 89, 88, 217, 195, 149, 59, 214, 193, 15, 14, 233, 5, 54, 123, 163, 206, 230, 62, 124, 135, 180, 118, 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