Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd371c72246bbbdf6df08932c8010782a8e6dbe3c73ef41def312761cae9b3b5

Tx prefix hash: b3bee309c0e2009d49d801e4e715d0e51caa2deea363f27730cf1863718ff179
Tx public key: e3c0888cc38a8b385b62589707815bf2e5db7f572b4b978124761f02cb9272d2
Timestamp: 1648380449 Timestamp [UCT]: 2022-03-27 11:27:29 Age [y:d:h:m:s]: 02:353:04:26:03
Block: 467446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 771784 RingCT/type: yes/0
Extra: 01e3c0888cc38a8b385b62589707815bf2e5db7f572b4b978124761f02cb9272d2021100000009d3fcec30000000000000000000

1 output(s) for total of 17.344333241000 dcy

stealth address amount amount idx
00: 9c1089ee2b2c616d4123fb6a035a06ff65830bf392731190a2eddce79a6e11ea 17.344333241000 885951 of 0

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": 467456, "vin": [ { "gen": { "height": 467446 } } ], "vout": [ { "amount": 17344333241, "target": { "key": "9c1089ee2b2c616d4123fb6a035a06ff65830bf392731190a2eddce79a6e11ea" } } ], "extra": [ 1, 227, 192, 136, 140, 195, 138, 139, 56, 91, 98, 88, 151, 7, 129, 91, 242, 229, 219, 127, 87, 43, 75, 151, 129, 36, 118, 31, 2, 203, 146, 114, 210, 2, 17, 0, 0, 0, 9, 211, 252, 236, 48, 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