Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55a9ac0e3ae3cde489b35dc9c6411e5a12ce259c990cd76f7423d599b471b59b

Tx prefix hash: 3dd9a99bbd2949f263a642ac39e3fb6940f63b0f44a45dd47e56f83f1889f124
Tx public key: 058c2d79e4b2f034d30f9048d166d74f40285281a1e86ed8dae9218cc46e4e87
Timestamp: 1608338710 Timestamp [UCT]: 2020-12-19 00:45:10 Age [y:d:h:m:s]: 03:334:22:32:21
Block: 164794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 991215 RingCT/type: yes/0
Extra: 01058c2d79e4b2f034d30f9048d166d74f40285281a1e86ed8dae9218cc46e4e87021100000088b9b01d0b000000000000000000

1 output(s) for total of 174.570052359000 dcy

stealth address amount amount idx
00: 7dee0e164b44de05f29d7ae9f21f9e80da05082332fdd50f22984e7f2cbfc319 174.570052359000 298657 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": 164804, "vin": [ { "gen": { "height": 164794 } } ], "vout": [ { "amount": 174570052359, "target": { "key": "7dee0e164b44de05f29d7ae9f21f9e80da05082332fdd50f22984e7f2cbfc319" } } ], "extra": [ 1, 5, 140, 45, 121, 228, 178, 240, 52, 211, 15, 144, 72, 209, 102, 215, 79, 64, 40, 82, 129, 161, 232, 110, 216, 218, 233, 33, 140, 196, 110, 78, 135, 2, 17, 0, 0, 0, 136, 185, 176, 29, 11, 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