Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351a606f58a456465d3b5af8d1e7babdbe3e65db09899392252cf063012a854b

Tx prefix hash: 0654dc933bc9ca2f7c44d32b7437c8e9fbb252ae0e9f9a8508616a121fedc7bd
Tx public key: 80af060272e0a9946fc6e5e0f3145a607054754f6e0f8ae67dc459666469c3aa
Timestamp: 1673147938 Timestamp [UCT]: 2023-01-08 03:18:58 Age [y:d:h:m:s]: 02:142:03:23:29
Block: 669981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 623333 RingCT/type: yes/0
Extra: 0180af060272e0a9946fc6e5e0f3145a607054754f6e0f8ae67dc459666469c3aa02110000000352542ceb000000000000000000

1 output(s) for total of 3.698918666000 dcy

stealth address amount amount idx
00: eba5bffe2de1723c4457adb126617161473f3d53cd03341d45d9935412bed123 3.698918666000 1111350 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": 669991, "vin": [ { "gen": { "height": 669981 } } ], "vout": [ { "amount": 3698918666, "target": { "key": "eba5bffe2de1723c4457adb126617161473f3d53cd03341d45d9935412bed123" } } ], "extra": [ 1, 128, 175, 6, 2, 114, 224, 169, 148, 111, 198, 229, 224, 243, 20, 90, 96, 112, 84, 117, 79, 110, 15, 138, 230, 125, 196, 89, 102, 100, 105, 195, 170, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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