Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65fe7645494fd44ff2fb35fadcec81699c374a3846a22860aba4a718c0a09920

Tx prefix hash: af73480b8568e499d489e400b843095ee10e2b521891c30f2d6cf8f7ab50ec21
Tx public key: af7d5faf8396a1ad6ef8b465eb1402eab4175c377d1d5558c840da1002b27928
Timestamp: 1736828093 Timestamp [UCT]: 2025-01-14 04:14:53 Age [y:d:h:m:s]: 00:155:08:21:54
Block: 1196930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110728 RingCT/type: yes/0
Extra: 01af7d5faf8396a1ad6ef8b465eb1402eab4175c377d1d5558c840da1002b279280211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a97aa3b8c5e3d5d72bda7c043f887f37f3a9f1192d3a229a7459d2c1c95a9982 0.600000000000 1683535 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": 1196940, "vin": [ { "gen": { "height": 1196930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a97aa3b8c5e3d5d72bda7c043f887f37f3a9f1192d3a229a7459d2c1c95a9982" } } ], "extra": [ 1, 175, 125, 95, 175, 131, 150, 161, 173, 110, 248, 180, 101, 235, 20, 2, 234, 180, 23, 92, 55, 125, 29, 85, 88, 200, 64, 218, 16, 2, 178, 121, 40, 2, 17, 0, 0, 0, 1, 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