Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9cbdd92362f1ad6bceb6b9e02e1357685605d44a99fc19ccfef5da433db46f9

Tx prefix hash: 568a927ec9b5bcddaae90fa33004b9fdec1f4011ad939bff7f0ac8e554f8a665
Tx public key: 79412023b234d6cbcbb3fdba89873e950781f79e7c671bd4d1ebda63ebc63309
Timestamp: 1723790171 Timestamp [UCT]: 2024-08-16 06:36:11 Age [y:d:h:m:s]: 00:192:11:31:48
Block: 1088978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137405 RingCT/type: yes/0
Extra: 0179412023b234d6cbcbb3fdba89873e950781f79e7c671bd4d1ebda63ebc63309021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 205d1c757f5bbb71b9e6f4ac67a8d6cd0d81c6d1d82655958eb471e0b7ad2541 0.600000000000 1563597 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": 1088988, "vin": [ { "gen": { "height": 1088978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "205d1c757f5bbb71b9e6f4ac67a8d6cd0d81c6d1d82655958eb471e0b7ad2541" } } ], "extra": [ 1, 121, 65, 32, 35, 178, 52, 214, 203, 203, 179, 253, 186, 137, 135, 62, 149, 7, 129, 247, 158, 124, 103, 27, 212, 209, 235, 218, 99, 235, 198, 51, 9, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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