Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e1f42f08f6e710acce4420f52de03f1456ef0655cb8ee11923d89a834beb502

Tx prefix hash: fbe5d30a4ec1c85a40380551e80712189b4a09782da7612c6b7c94432cc96f11
Tx public key: 337d32d442adc653f828e5b82523161b3d3d4235ab3ab30c1fe5de09b37a1951
Timestamp: 1579237270 Timestamp [UCT]: 2020-01-17 05:01:10 Age [y:d:h:m:s]: 05:082:23:44:13
Block: 47406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1209330 RingCT/type: yes/0
Extra: 01337d32d442adc653f828e5b82523161b3d3d4235ab3ab30c1fe5de09b37a195102110000002e391a8d0e000000000000000000

1 output(s) for total of 427.489133401000 dcy

stealth address amount amount idx
00: 3bae6767f93401c829aee00608057d6ec2d654acc8ca75cbf1a468f2bb04431a 427.489133401000 87577 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": 47416, "vin": [ { "gen": { "height": 47406 } } ], "vout": [ { "amount": 427489133401, "target": { "key": "3bae6767f93401c829aee00608057d6ec2d654acc8ca75cbf1a468f2bb04431a" } } ], "extra": [ 1, 51, 125, 50, 212, 66, 173, 198, 83, 248, 40, 229, 184, 37, 35, 22, 27, 61, 61, 66, 53, 171, 58, 179, 12, 31, 229, 222, 9, 179, 122, 25, 81, 2, 17, 0, 0, 0, 46, 57, 26, 141, 14, 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