Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9fd855182241c1c06280a7b56b69dbe7a21f54034c714601ec6d74128c1b60b

Tx prefix hash: 6a51c6f00239a218954299dda0fb71fd36cf13336c45d19eba3dc78a3f79c456
Tx public key: ec0b4404a131ea257cf7315af115e19cc043c4737637b94a5edf817c893fa961
Timestamp: 1632848811 Timestamp [UCT]: 2021-09-28 17:06:51 Age [y:d:h:m:s]: 03:038:19:33:19
Block: 342641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 804444 RingCT/type: yes/0
Extra: 01ec0b4404a131ea257cf7315af115e19cc043c4737637b94a5edf817c893fa96102110000000ea272b9cb000000000000000000

1 output(s) for total of 44.946522653000 dcy

stealth address amount amount idx
00: ff06a0a1f646c233879c334bc733d7b6ab3db577d8dbfa514e5fce93271be14a 44.946522653000 703609 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": 342651, "vin": [ { "gen": { "height": 342641 } } ], "vout": [ { "amount": 44946522653, "target": { "key": "ff06a0a1f646c233879c334bc733d7b6ab3db577d8dbfa514e5fce93271be14a" } } ], "extra": [ 1, 236, 11, 68, 4, 161, 49, 234, 37, 124, 247, 49, 90, 241, 21, 225, 156, 192, 67, 196, 115, 118, 55, 185, 74, 94, 223, 129, 124, 137, 63, 169, 97, 2, 17, 0, 0, 0, 14, 162, 114, 185, 203, 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