Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65880d99954fe4fe65372c0613732d728314a48c4cf0797af7f7d971aa849620

Tx prefix hash: c8bf8a7ea0055ed0b3cdb89028f1c850717a18d9a5d4847143db6bf9374c96a1
Tx public key: fee0b8340a6a38e3aad95edc05da8591d868df3aaa469a9ea47bbec03e5b7f8f
Timestamp: 1733569521 Timestamp [UCT]: 2024-12-07 11:05:21 Age [y:d:h:m:s]: 00:194:05:43:53
Block: 1169952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138540 RingCT/type: yes/0
Extra: 01fee0b8340a6a38e3aad95edc05da8591d868df3aaa469a9ea47bbec03e5b7f8f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e706fad9fc90781620c0a424e148d44c1ee96573bce519eb905e632631c8f75e 0.600000000000 1655679 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": 1169962, "vin": [ { "gen": { "height": 1169952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e706fad9fc90781620c0a424e148d44c1ee96573bce519eb905e632631c8f75e" } } ], "extra": [ 1, 254, 224, 184, 52, 10, 106, 56, 227, 170, 217, 94, 220, 5, 218, 133, 145, 216, 104, 223, 58, 170, 70, 154, 158, 164, 123, 190, 192, 62, 91, 127, 143, 2, 17, 0, 0, 0, 4, 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