Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 419b8815638ea1fe161ba5a4458d0b1f48884514f97016d446886db78add71e2

Tx prefix hash: ca56a88f1466bf4962be833ea3bc327fa7b21f456f4a57d075763153f9f61f59
Tx public key: e940b1e4f91ca12b7232409c8561f84dd60c28d9ae13e53ab661efa4da47fe2f
Timestamp: 1707375327 Timestamp [UCT]: 2024-02-08 06:55:27 Age [y:d:h:m:s]: 01:134:05:07:39
Block: 952879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356859 RingCT/type: yes/0
Extra: 01e940b1e4f91ca12b7232409c8561f84dd60c28d9ae13e53ab661efa4da47fe2f02110000000810a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d770b2d1fd01ff4f7aedf8b3987731aaa887be7c24a06d1ec3d8e79cde4f4fa 0.600000000000 1412015 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": 952889, "vin": [ { "gen": { "height": 952879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d770b2d1fd01ff4f7aedf8b3987731aaa887be7c24a06d1ec3d8e79cde4f4fa" } } ], "extra": [ 1, 233, 64, 177, 228, 249, 28, 161, 43, 114, 50, 64, 156, 133, 97, 248, 77, 214, 12, 40, 217, 174, 19, 229, 58, 182, 97, 239, 164, 218, 71, 254, 47, 2, 17, 0, 0, 0, 8, 16, 161, 116, 143, 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