Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1795212fc99e7cdaa544d5d0b827a69b41f10f386ef7277fc1fba621beb30d58

Tx prefix hash: f2bfef4da9f341dd4d20ec08d6df96832d888c74066bb1d9925b2499b0f1db46
Tx public key: 9b80e1d86597aa889f89845311d6424b3aa9c2f1d9032f771b00e82fdd4277cf
Timestamp: 1694246143 Timestamp [UCT]: 2023-09-09 07:55:43 Age [y:d:h:m:s]: 01:171:05:02:47
Block: 844225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383444 RingCT/type: yes/0
Extra: 019b80e1d86597aa889f89845311d6424b3aa9c2f1d9032f771b00e82fdd4277cf02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.978886154000 dcy

stealth address amount amount idx
00: 9b1ac8d6c77b0deedc0ed018dc00cd6ec3584dc0f9d6c813b7e244e10488fb00 0.978886154000 1297521 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": 844235, "vin": [ { "gen": { "height": 844225 } } ], "vout": [ { "amount": 978886154, "target": { "key": "9b1ac8d6c77b0deedc0ed018dc00cd6ec3584dc0f9d6c813b7e244e10488fb00" } } ], "extra": [ 1, 155, 128, 225, 216, 101, 151, 170, 136, 159, 137, 132, 83, 17, 214, 66, 75, 58, 169, 194, 241, 217, 3, 47, 119, 27, 0, 232, 47, 221, 66, 119, 207, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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