Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c1faf752b16a58f378727020e578aee9516c875c7efbd33677d72ce48c754d6

Tx prefix hash: 46141dbd1ac7fb6b59bf2f2a60191f4a12aee6f4705859383f7c1f2f5ac58cd4
Tx public key: 0631e0d508210d6cc23dbd5eeb86fd5e263ef9d951bd5e8caef51fde1fa58b6d
Timestamp: 1703889526 Timestamp [UCT]: 2023-12-29 22:38:46 Age [y:d:h:m:s]: 01:102:04:59:04
Block: 923985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334172 RingCT/type: yes/0
Extra: 010631e0d508210d6cc23dbd5eeb86fd5e263ef9d951bd5e8caef51fde1fa58b6d02110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d6a3af1dd5d629f27b571c2398315c615e6fe5dc6d7bf52447b46551fe4a01c 0.600000000000 1381727 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": 923995, "vin": [ { "gen": { "height": 923985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d6a3af1dd5d629f27b571c2398315c615e6fe5dc6d7bf52447b46551fe4a01c" } } ], "extra": [ 1, 6, 49, 224, 213, 8, 33, 13, 108, 194, 61, 189, 94, 235, 134, 253, 94, 38, 62, 249, 217, 81, 189, 94, 140, 174, 245, 31, 222, 31, 165, 139, 109, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 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