Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bccddf25fcf2f7c08debf59e1e3298bade72959d776ac048edd9b735ad72b223

Tx prefix hash: 8673323baf28dbc7f1ac2af9204bd8ccaa2ae68b0fd2eee5172b6701c5426d13
Tx public key: 84df76e2c1b0c660a742bc60c60f2d20aa1afc025429a5e49f4827d7870d07bd
Timestamp: 1729503448 Timestamp [UCT]: 2024-10-21 09:37:28 Age [y:d:h:m:s]: 00:185:14:20:23
Block: 1136308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132471 RingCT/type: yes/0
Extra: 0184df76e2c1b0c660a742bc60c60f2d20aa1afc025429a5e49f4827d7870d07bd021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fe454e846a496d051ee34e630bdb22ef53f2831ab3e153da7a51afdd3c85319 0.600000000000 1619653 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": 1136318, "vin": [ { "gen": { "height": 1136308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fe454e846a496d051ee34e630bdb22ef53f2831ab3e153da7a51afdd3c85319" } } ], "extra": [ 1, 132, 223, 118, 226, 193, 176, 198, 96, 167, 66, 188, 96, 198, 15, 45, 32, 170, 26, 252, 2, 84, 41, 165, 228, 159, 72, 39, 215, 135, 13, 7, 189, 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