Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90d1fd327bea1baf8b43c3b7e5f716a43a5af61b4d84290aff44e4641e4407b1

Tx prefix hash: 4c27f62a3e31d305843da206d6133e2ddb6ff3028b765689ae97514da7fd716d
Tx public key: 8ffd6c0784ff1b7e12990e6fd84acf37e0b52b719f93582bd7494df3d3469c5a
Timestamp: 1682821143 Timestamp [UCT]: 2023-04-30 02:19:03 Age [y:d:h:m:s]: 01:256:17:35:50
Block: 749578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444954 RingCT/type: yes/0
Extra: 018ffd6c0784ff1b7e12990e6fd84acf37e0b52b719f93582bd7494df3d3469c5a021100000002b3164c24000000000000000000

1 output(s) for total of 2.015288029000 dcy

stealth address amount amount idx
00: f0970cc36d3038af7d0af80d21a8e4982ae3304ff743ca8083024ef2681219b5 2.015288029000 1197561 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": 749588, "vin": [ { "gen": { "height": 749578 } } ], "vout": [ { "amount": 2015288029, "target": { "key": "f0970cc36d3038af7d0af80d21a8e4982ae3304ff743ca8083024ef2681219b5" } } ], "extra": [ 1, 143, 253, 108, 7, 132, 255, 27, 126, 18, 153, 14, 111, 216, 74, 207, 55, 224, 181, 43, 113, 159, 147, 88, 43, 215, 73, 77, 243, 211, 70, 156, 90, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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