Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 049f9a97501c316243ad8de965ee7283e3f1dafc4e4e9ef3f181b219ad3237e1

Tx prefix hash: aa7c69fcb1faaaaeb9a6afe9f61464e1f6f6be01f62dde2869f4a53920c86bbd
Tx public key: 9cfce2584165ce83b9eb383985111f8f6ef9ac1de13e69bf0be244d96ba2217e
Timestamp: 1737088494 Timestamp [UCT]: 2025-01-17 04:34:54 Age [y:d:h:m:s]: 00:307:19:46:54
Block: 1199077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217502 RingCT/type: yes/0
Extra: 019cfce2584165ce83b9eb383985111f8f6ef9ac1de13e69bf0be244d96ba2217e02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 449290fd51cc7b1c84d93e9aa9756720d8860d2472dca2f5f6d9d4d72075c63b 0.600000000000 1685706 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": 1199087, "vin": [ { "gen": { "height": 1199077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "449290fd51cc7b1c84d93e9aa9756720d8860d2472dca2f5f6d9d4d72075c63b" } } ], "extra": [ 1, 156, 252, 226, 88, 65, 101, 206, 131, 185, 235, 56, 57, 133, 17, 31, 143, 110, 249, 172, 29, 225, 62, 105, 191, 11, 226, 68, 217, 107, 162, 33, 126, 2, 17, 0, 0, 0, 10, 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