Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1e48d4b11c9dfcb74b0ccaf147b9605cf3cb98409a119256750a64292a19e2

Tx prefix hash: 0b2a62ab345d92bb2fd85b26dd207ef095c8e1fac2a4e5e4093cb8bf54962449
Tx public key: 91e8bb44d6311fadd7bbbbf6e3d29530b5a5d9f84481df2c0e9f4e6d79e528f1
Timestamp: 1617751044 Timestamp [UCT]: 2021-04-06 23:17:24 Age [y:d:h:m:s]: 03:266:02:52:28
Block: 234666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 950030 RingCT/type: yes/0
Extra: 0191e8bb44d6311fadd7bbbbf6e3d29530b5a5d9f84481df2c0e9f4e6d79e528f10211000000047071732b000000000000000000

1 output(s) for total of 102.436493156000 dcy

stealth address amount amount idx
00: 9289143f1cee5dac507697a463058ea33fd849d42354907cf0c06b371fc12052 102.436493156000 487240 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": 234676, "vin": [ { "gen": { "height": 234666 } } ], "vout": [ { "amount": 102436493156, "target": { "key": "9289143f1cee5dac507697a463058ea33fd849d42354907cf0c06b371fc12052" } } ], "extra": [ 1, 145, 232, 187, 68, 214, 49, 31, 173, 215, 187, 187, 246, 227, 210, 149, 48, 181, 165, 217, 248, 68, 129, 223, 44, 14, 159, 78, 109, 121, 229, 40, 241, 2, 17, 0, 0, 0, 4, 112, 113, 115, 43, 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