Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc972d55eb8b7e9d8c13079ff498cd6115137d55621ef414ae1d015ea1aafd4b

Tx prefix hash: 4459de80bef8f287ad48868c16345fa616e7e4cbf36a1af74d75c0c35e99b143
Tx public key: f9910e7b372d8a55ce303187124dc399328dabb3616ff6eb2a3d7911cababe12
Timestamp: 1652033309 Timestamp [UCT]: 2022-05-08 18:08:29 Age [y:d:h:m:s]: 02:313:17:08:30
Block: 496889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744352 RingCT/type: yes/0
Extra: 01f9910e7b372d8a55ce303187124dc399328dabb3616ff6eb2a3d7911cababe1202110000000fbf7ee4e7000000000000000000

1 output(s) for total of 13.854813517000 dcy

stealth address amount amount idx
00: 2eee93bd5beb281229138c5eaee9a5c3b91cbbf21a4ed662d7ac9044d21d577a 13.854813517000 920898 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": 496899, "vin": [ { "gen": { "height": 496889 } } ], "vout": [ { "amount": 13854813517, "target": { "key": "2eee93bd5beb281229138c5eaee9a5c3b91cbbf21a4ed662d7ac9044d21d577a" } } ], "extra": [ 1, 249, 145, 14, 123, 55, 45, 138, 85, 206, 48, 49, 135, 18, 77, 195, 153, 50, 141, 171, 179, 97, 111, 246, 235, 42, 61, 121, 17, 202, 186, 190, 18, 2, 17, 0, 0, 0, 15, 191, 126, 228, 231, 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