Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58fc63c4ad2edc8da3acab16ccce5cbdbbbf62d012314331d069e1ac1a2d99d2

Tx prefix hash: 8d46ac0229de0762370ffaad8543939174622c76c4fb8fd0908958dc1e42c1bb
Tx public key: 68ccee3b47ff655c065ddc04c636c7a971be35185e4e61439f2e60b7680e9b39
Timestamp: 1697204669 Timestamp [UCT]: 2023-10-13 13:44:29 Age [y:d:h:m:s]: 01:108:10:45:47
Block: 868774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338513 RingCT/type: yes/0
Extra: 0168ccee3b47ff655c065ddc04c636c7a971be35185e4e61439f2e60b7680e9b39021100000002faf35c9c000000000000000000

1 output(s) for total of 0.811691731000 dcy

stealth address amount amount idx
00: 023fb473cccfcb1dbdd48b3577c3f9a16a894a2caac982fcf66be2af2be63836 0.811691731000 1323593 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": 868784, "vin": [ { "gen": { "height": 868774 } } ], "vout": [ { "amount": 811691731, "target": { "key": "023fb473cccfcb1dbdd48b3577c3f9a16a894a2caac982fcf66be2af2be63836" } } ], "extra": [ 1, 104, 204, 238, 59, 71, 255, 101, 92, 6, 93, 220, 4, 198, 54, 199, 169, 113, 190, 53, 24, 94, 78, 97, 67, 159, 46, 96, 183, 104, 14, 155, 57, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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