Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bcb877d4ee26240f22ef18f508080150ad66d2be1ec1d5f4acb4a3eb9bed0f8

Tx prefix hash: 958b50361223d094b4f434f86a6f1b373457f869855716593f8fc0e3d36edfd2
Tx public key: 5a1d923010e537e121c4daf86e73014a1108b07a4ff9a1bb05e034d96d9e9a0a
Timestamp: 1711509897 Timestamp [UCT]: 2024-03-27 03:24:57 Age [y:d:h:m:s]: 01:053:19:38:33
Block: 987192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299428 RingCT/type: yes/0
Extra: 015a1d923010e537e121c4daf86e73014a1108b07a4ff9a1bb05e034d96d9e9a0a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9607f3a25ee8a88bc19f02c1b0a867c617dca7409b14a0a9adad908326373d87 0.600000000000 1447433 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": 987202, "vin": [ { "gen": { "height": 987192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9607f3a25ee8a88bc19f02c1b0a867c617dca7409b14a0a9adad908326373d87" } } ], "extra": [ 1, 90, 29, 146, 48, 16, 229, 55, 225, 33, 196, 218, 248, 110, 115, 1, 74, 17, 8, 176, 122, 79, 249, 161, 187, 5, 224, 52, 217, 109, 158, 154, 10, 2, 17, 0, 0, 0, 2, 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