Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14a056bd031df90191c3c61a13583da6dae998bfdc66f90b56d64717c1b13c47

Tx prefix hash: 9b7356f2bbed914b837130549f6b16afe0723652cd77e6d9742924ed1ab015c7
Tx public key: b10e64d8a09bc2eb79e5c99791656e24c0c144d0f1e21e893f79ceb168f63369
Timestamp: 1703320407 Timestamp [UCT]: 2023-12-23 08:33:27 Age [y:d:h:m:s]: 01:144:20:35:40
Block: 919275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364659 RingCT/type: yes/0
Extra: 01b10e64d8a09bc2eb79e5c99791656e24c0c144d0f1e21e893f79ceb168f6336902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 683a4f14795813fd217179ea99371637bf5f2d052e06ffc66c8e29a0ac9c35d7 0.600000000000 1376941 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": 919285, "vin": [ { "gen": { "height": 919275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "683a4f14795813fd217179ea99371637bf5f2d052e06ffc66c8e29a0ac9c35d7" } } ], "extra": [ 1, 177, 14, 100, 216, 160, 155, 194, 235, 121, 229, 201, 151, 145, 101, 110, 36, 192, 193, 68, 208, 241, 226, 30, 137, 63, 121, 206, 177, 104, 246, 51, 105, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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