Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc56a4f21a5a8346029d5ba01244ff40b2dd099d20ac08c2060b630dc13d517f

Tx prefix hash: b5ef6689f6d607c2b55af381d8832a5ba193c80f70ef937734236361cbca9624
Tx public key: 2eb7102415ef59f8434ae7f28b751dce145e19a2967dd2e359259e0ad0b0d10d
Timestamp: 1686388053 Timestamp [UCT]: 2023-06-10 09:07:33 Age [y:d:h:m:s]: 01:218:07:45:10
Block: 779151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417441 RingCT/type: yes/0
Extra: 012eb7102415ef59f8434ae7f28b751dce145e19a2967dd2e359259e0ad0b0d10d02110000000333af99f4000000000000000000

1 output(s) for total of 1.608234804000 dcy

stealth address amount amount idx
00: 4cb68410e9080129ac5843c05583d155404d9ecf2320aa99fa43fe42dd7d66d2 1.608234804000 1228796 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": 779161, "vin": [ { "gen": { "height": 779151 } } ], "vout": [ { "amount": 1608234804, "target": { "key": "4cb68410e9080129ac5843c05583d155404d9ecf2320aa99fa43fe42dd7d66d2" } } ], "extra": [ 1, 46, 183, 16, 36, 21, 239, 89, 248, 67, 74, 231, 242, 139, 117, 29, 206, 20, 94, 25, 162, 150, 125, 210, 227, 89, 37, 158, 10, 208, 176, 209, 13, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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