Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd5df8819e2cf41efcb0df21cafe86d5cc470bf12ff4ad516a88e738f923f237

Tx prefix hash: 21829e759c0ec5bfa7134638c4350e41370128aa1c3b600e414c06e6a3a39587
Tx public key: 3d818a85b343545f47bb462c540bcdbc9fae1a6569cb0627480929a0b24e6779
Timestamp: 1731584301 Timestamp [UCT]: 2024-11-14 11:38:21 Age [y:d:h:m:s]: 00:328:11:33:39
Block: 1153505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232254 RingCT/type: yes/0
Extra: 013d818a85b343545f47bb462c540bcdbc9fae1a6569cb0627480929a0b24e6779021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18226da2c70c5d365225a0e76d384d06b6948a8826b4394f6a4646df78d13838 0.600000000000 1639114 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": 1153515, "vin": [ { "gen": { "height": 1153505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18226da2c70c5d365225a0e76d384d06b6948a8826b4394f6a4646df78d13838" } } ], "extra": [ 1, 61, 129, 138, 133, 179, 67, 84, 95, 71, 187, 70, 44, 84, 11, 205, 188, 159, 174, 26, 101, 105, 203, 6, 39, 72, 9, 41, 160, 178, 78, 103, 121, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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