Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bb3d9bf98ef3cec4b899804ca7b0b428c131e4018fb4d07a5e388dc60c85a7e

Tx prefix hash: a38de9c13aee03122f0342bc50e006b0016c651ff8e4f9d079b2149afe68a942
Tx public key: 50627f520fe54fb1608eda2a5c8507f3cef9430d444271a02b9a2625c800fd35
Timestamp: 1721012872 Timestamp [UCT]: 2024-07-15 03:07:52 Age [y:d:h:m:s]: 00:196:16:09:04
Block: 1065962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140468 RingCT/type: yes/0
Extra: 0150627f520fe54fb1608eda2a5c8507f3cef9430d444271a02b9a2625c800fd3502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a94f8654d263632f062b74cdf7a1f5386941a7c80fbef558cfa429941e86f33 0.600000000000 1536531 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": 1065972, "vin": [ { "gen": { "height": 1065962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a94f8654d263632f062b74cdf7a1f5386941a7c80fbef558cfa429941e86f33" } } ], "extra": [ 1, 80, 98, 127, 82, 15, 229, 79, 177, 96, 142, 218, 42, 92, 133, 7, 243, 206, 249, 67, 13, 68, 66, 113, 160, 43, 154, 38, 37, 200, 0, 253, 53, 2, 17, 0, 0, 0, 4, 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