Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beb8610673257054bf50d1812550b84fcb413d3cbf82e3a1bce3835bdca6548d

Tx prefix hash: eac74ac3bef301e9d549cf7651403701d7397dadd2ff8331342d3824c1ae4b02
Tx public key: 3b7befadad8f7ecf5c727a6df910e15fefceeacaf4ae83fae9908c7c8c0077db
Timestamp: 1728841049 Timestamp [UCT]: 2024-10-13 17:37:29 Age [y:d:h:m:s]: 00:101:19:36:50
Block: 1130853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72735 RingCT/type: yes/0
Extra: 013b7befadad8f7ecf5c727a6df910e15fefceeacaf4ae83fae9908c7c8c0077db02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9a3568dfdd3a47e715a9b834ccda9356d28d9833992213bcdbae3ce698c6f6f 0.600000000000 1613734 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": 1130863, "vin": [ { "gen": { "height": 1130853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9a3568dfdd3a47e715a9b834ccda9356d28d9833992213bcdbae3ce698c6f6f" } } ], "extra": [ 1, 59, 123, 239, 173, 173, 143, 126, 207, 92, 114, 122, 109, 249, 16, 225, 95, 239, 206, 234, 202, 244, 174, 131, 250, 233, 144, 140, 124, 140, 0, 119, 219, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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