Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1837c9995901c1c0206c3c55e0b825f34cda34721825a04c0079ab513376b2

Tx prefix hash: dcf27c8acb5d879aba2e9274262dcb98fb62585dc31046bc3834727a7d475f86
Tx public key: e484ac5b5f45447f26e2a120b02536bcb8ffdcfa1aef3053beb0dec90eb7beab
Timestamp: 1729343422 Timestamp [UCT]: 2024-10-19 13:10:22 Age [y:d:h:m:s]: 00:189:02:26:02
Block: 1135006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134954 RingCT/type: yes/0
Extra: 01e484ac5b5f45447f26e2a120b02536bcb8ffdcfa1aef3053beb0dec90eb7beab021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7f820cc536953764a2ecbbca9de5e0e7100d8daac0fc0e4aafb9ff1f62970d8 0.600000000000 1618335 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": 1135016, "vin": [ { "gen": { "height": 1135006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7f820cc536953764a2ecbbca9de5e0e7100d8daac0fc0e4aafb9ff1f62970d8" } } ], "extra": [ 1, 228, 132, 172, 91, 95, 69, 68, 127, 38, 226, 161, 32, 176, 37, 54, 188, 184, 255, 220, 250, 26, 239, 48, 83, 190, 176, 222, 201, 14, 183, 190, 171, 2, 17, 0, 0, 0, 4, 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