Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a7eb127f581c482b1ed70d7be159326b54ea04a6f9dbba6a01ab924423d971a

Tx prefix hash: 00ff10c99c8db1d60ca86fa7b56d9b8c875590cebf767c6a2682eb9a0aae2793
Tx public key: c95d44c47214af8ef779c53ecf9e675deb59f56d68ddef4cdcc05984cb826fef
Timestamp: 1729330399 Timestamp [UCT]: 2024-10-19 09:33:19 Age [y:d:h:m:s]: 00:188:17:25:27
Block: 1134908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134666 RingCT/type: yes/0
Extra: 01c95d44c47214af8ef779c53ecf9e675deb59f56d68ddef4cdcc05984cb826fef02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 394fdfd593e338d6941002d628061788c831b02af8863eab1c16d9fdab725a0e 0.600000000000 1618235 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": 1134918, "vin": [ { "gen": { "height": 1134908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "394fdfd593e338d6941002d628061788c831b02af8863eab1c16d9fdab725a0e" } } ], "extra": [ 1, 201, 93, 68, 196, 114, 20, 175, 142, 247, 121, 197, 62, 207, 158, 103, 93, 235, 89, 245, 109, 104, 221, 239, 76, 220, 192, 89, 132, 203, 130, 111, 239, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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