Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 279b50fc8d17c8edf76dd097cef703ac91e00f4ab1502829e690f4c0d31b112f

Tx prefix hash: b255a57d09415472acfc9ad4896bd29f16488e9c60ac862fffe6f1cfc3606a02
Tx public key: ef4cb9480765e9a4f6fd5dcf299c1966cd8f4c0d109e636d923266cdd8eba5b5
Timestamp: 1738640497 Timestamp [UCT]: 2025-02-04 03:41:37 Age [y:d:h:m:s]: 00:332:18:58:36
Block: 1211654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235683 RingCT/type: yes/0
Extra: 01ef4cb9480765e9a4f6fd5dcf299c1966cd8f4c0d109e636d923266cdd8eba5b5021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a1a6bd71677610f9afaffd597bbb69522421591321fc701c4a8f63262270b92 0.600000000000 1698417 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": 1211664, "vin": [ { "gen": { "height": 1211654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a1a6bd71677610f9afaffd597bbb69522421591321fc701c4a8f63262270b92" } } ], "extra": [ 1, 239, 76, 185, 72, 7, 101, 233, 164, 246, 253, 93, 207, 41, 156, 25, 102, 205, 143, 76, 13, 16, 158, 99, 109, 146, 50, 102, 205, 216, 235, 165, 181, 2, 17, 0, 0, 0, 6, 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