Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b302bbf5a76a53bcc4140258bfef06cef17b3e27cbed2cf2aa051f5f19f00a3

Tx prefix hash: 4fc95d293f4f4c9b350653786c7a23a395a0ee2b53c5d75b81d9396da9db17c3
Tx public key: 51cbf1bbe3cb476507af37116b71c13076c844e8035a856b31b8d0d1a56882fc
Timestamp: 1729870300 Timestamp [UCT]: 2024-10-25 15:31:40 Age [y:d:h:m:s]: 00:162:10:39:57
Block: 1139346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115898 RingCT/type: yes/0
Extra: 0151cbf1bbe3cb476507af37116b71c13076c844e8035a856b31b8d0d1a56882fc021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6af2e0d12fbbc14e5202cc292e81a68b1a09628967e4c984bf138a3da92a59f 0.600000000000 1623133 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": 1139356, "vin": [ { "gen": { "height": 1139346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6af2e0d12fbbc14e5202cc292e81a68b1a09628967e4c984bf138a3da92a59f" } } ], "extra": [ 1, 81, 203, 241, 187, 227, 203, 71, 101, 7, 175, 55, 17, 107, 113, 193, 48, 118, 200, 68, 232, 3, 90, 133, 107, 49, 184, 208, 209, 165, 104, 130, 252, 2, 17, 0, 0, 0, 2, 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