Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 080e1450cc71605325d9257b47822e702c4e4222da3b675aeff3645b502dd6be

Tx prefix hash: afd012559fcd34b1acde363b576f18d927eafcc33931030ab50ec228c7bded2a
Tx public key: 349cb4afab72c1b7365f5a8aeeef24b45abccb8043d0919d48d606fa3f13b1a2
Timestamp: 1702276681 Timestamp [UCT]: 2023-12-11 06:38:01 Age [y:d:h:m:s]: 01:119:07:28:19
Block: 910616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346411 RingCT/type: yes/0
Extra: 01349cb4afab72c1b7365f5a8aeeef24b45abccb8043d0919d48d606fa3f13b1a202110000000afaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4a0b3f2d21b668a7a7ba0c1b8f721afe2021ee7d6dff40044ef11f9015a9612 0.600000000000 1367777 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": 910626, "vin": [ { "gen": { "height": 910616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4a0b3f2d21b668a7a7ba0c1b8f721afe2021ee7d6dff40044ef11f9015a9612" } } ], "extra": [ 1, 52, 156, 180, 175, 171, 114, 193, 183, 54, 95, 90, 138, 238, 239, 36, 180, 90, 188, 203, 128, 67, 208, 145, 157, 72, 214, 6, 250, 63, 19, 177, 162, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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