Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10adacc2b9e241268988424596443fb5cd89bb028c9ed5bfba7d6bf68d2680a2

Tx prefix hash: 42abd4f16eef8170c180cea5a9d3fe155a955880becb2689c5f0dd502c402b43
Tx public key: 601b78a99c1d4a0ac7c9802b45b35af69aa1964b786c1a94d2616d5334573f73
Timestamp: 1717518752 Timestamp [UCT]: 2024-06-04 16:32:32 Age [y:d:h:m:s]: 00:149:01:01:09
Block: 1036994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106668 RingCT/type: yes/0
Extra: 01601b78a99c1d4a0ac7c9802b45b35af69aa1964b786c1a94d2616d5334573f7302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d61bf6e4655ee1fc35e0f7ddd0c7de886ef395f3af9d518c4e6f30a3bfb4a6e1 0.600000000000 1505525 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": 1037004, "vin": [ { "gen": { "height": 1036994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d61bf6e4655ee1fc35e0f7ddd0c7de886ef395f3af9d518c4e6f30a3bfb4a6e1" } } ], "extra": [ 1, 96, 27, 120, 169, 156, 29, 74, 10, 199, 201, 128, 43, 69, 179, 90, 246, 154, 161, 150, 75, 120, 108, 26, 148, 210, 97, 109, 83, 52, 87, 63, 115, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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