Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69dc91bb55c37ea5ce92f5318ef76e85842eab44d5c33e9a5f4812486e375ac0

Tx prefix hash: 34c1ab877d6918b4a44c342d0632bad2b86f4977b028abccd379d97b6fa9c5b5
Tx public key: ffcfab96309f212e2647b969f7dde99f4af822350ea6683301cd68466c905e04
Timestamp: 1722310713 Timestamp [UCT]: 2024-07-30 03:38:33 Age [y:d:h:m:s]: 00:247:16:21:09
Block: 1076710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176911 RingCT/type: yes/0
Extra: 01ffcfab96309f212e2647b969f7dde99f4af822350ea6683301cd68466c905e0402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b1f90a3a9a32c7aa2f20cb734d86e313c52ea560ed5cf51c5d6dfe8e64c0937 0.600000000000 1549251 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": 1076720, "vin": [ { "gen": { "height": 1076710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b1f90a3a9a32c7aa2f20cb734d86e313c52ea560ed5cf51c5d6dfe8e64c0937" } } ], "extra": [ 1, 255, 207, 171, 150, 48, 159, 33, 46, 38, 71, 185, 105, 247, 221, 233, 159, 74, 248, 34, 53, 14, 166, 104, 51, 1, 205, 104, 70, 108, 144, 94, 4, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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