Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b55095cf3988447eb6733f86b839aa834fba5da571a63ad5b420a21967da12bb

Tx prefix hash: cbf4a36cefc612f917714daae0df9e78c7b81e1c777a742e08dc40b018b26093
Tx public key: 0cf4af1f98e526d7c71e1a9bf8202c4333164449034322ef9825e93771dc5daf
Timestamp: 1700761042 Timestamp [UCT]: 2023-11-23 17:37:22 Age [y:d:h:m:s]: 01:351:07:25:07
Block: 898055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509964 RingCT/type: yes/0
Extra: 010cf4af1f98e526d7c71e1a9bf8202c4333164449034322ef9825e93771dc5daf0211000000044b8f5122000000000000000000

1 output(s) for total of 0.649188729000 dcy

stealth address amount amount idx
00: c6e08680c771bb12e7fcf065082c241eb4cf1c8905a8252b3cac00f9f8084ae1 0.649188729000 1354458 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": 898065, "vin": [ { "gen": { "height": 898055 } } ], "vout": [ { "amount": 649188729, "target": { "key": "c6e08680c771bb12e7fcf065082c241eb4cf1c8905a8252b3cac00f9f8084ae1" } } ], "extra": [ 1, 12, 244, 175, 31, 152, 229, 38, 215, 199, 30, 26, 155, 248, 32, 44, 67, 51, 22, 68, 73, 3, 67, 34, 239, 152, 37, 233, 55, 113, 220, 93, 175, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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