Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4638385adf45f22ebc07f4a4d8080f77094384ccf63264f2fe16f409888fb2d6

Tx prefix hash: 9657cd95a067a7b02f932adb131f23f44239e584b9fd2a2fa9438baed7370291
Tx public key: 98958792f8ef4809c2e9c43a12d5a09ecc8f5b30547cdd5042504a2ca77dba35
Timestamp: 1727194953 Timestamp [UCT]: 2024-09-24 16:22:33 Age [y:d:h:m:s]: 00:060:21:15:43
Block: 1117203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43518 RingCT/type: yes/0
Extra: 0198958792f8ef4809c2e9c43a12d5a09ecc8f5b30547cdd5042504a2ca77dba35021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51a8b3ed3225c5a909c4f9af197d3e54ea8bf30425a84c778a75ddbe014ea7be 0.600000000000 1597960 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": 1117213, "vin": [ { "gen": { "height": 1117203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51a8b3ed3225c5a909c4f9af197d3e54ea8bf30425a84c778a75ddbe014ea7be" } } ], "extra": [ 1, 152, 149, 135, 146, 248, 239, 72, 9, 194, 233, 196, 58, 18, 213, 160, 158, 204, 143, 91, 48, 84, 124, 221, 80, 66, 80, 74, 44, 167, 125, 186, 53, 2, 17, 0, 0, 0, 8, 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