Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb43693528814672f1de8fd34c530e29250f11f2240ec73371a6c131d5fe401d

Tx prefix hash: ffa26604291411145e0ccd16ca0bfc68cbf9b091498e5dbf011a0af96bf9a034
Tx public key: 6ba6b891f136cf5be5679c5dc77cf3b4f9f8895cd6b9d23cfc64e2da3de1f80f
Timestamp: 1719071504 Timestamp [UCT]: 2024-06-22 15:51:44 Age [y:d:h:m:s]: 00:308:05:07:30
Block: 1049844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220272 RingCT/type: yes/0
Extra: 016ba6b891f136cf5be5679c5dc77cf3b4f9f8895cd6b9d23cfc64e2da3de1f80f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c26df8b9b0814b04bcfb5efa6e33cdd5e75cf7fba69324ed39c83edc90c5709 0.600000000000 1519949 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": 1049854, "vin": [ { "gen": { "height": 1049844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c26df8b9b0814b04bcfb5efa6e33cdd5e75cf7fba69324ed39c83edc90c5709" } } ], "extra": [ 1, 107, 166, 184, 145, 241, 54, 207, 91, 229, 103, 156, 93, 199, 124, 243, 180, 249, 248, 137, 92, 214, 185, 210, 60, 252, 100, 226, 218, 61, 225, 248, 15, 2, 17, 0, 0, 0, 3, 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