Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1e76295c3f1a1bc3804b265e411bc537df64b77fb8272f8912008b7830b4e89

Tx prefix hash: e3390991a1c1416457037568c6eb8cd0c5fd29d15199e9bbcbf43a75f8c45a11
Tx public key: cedbcf0daced4e8481c458dc5b36797de551dc3b9c6cd635ca1902df791faf4d
Timestamp: 1632156162 Timestamp [UCT]: 2021-09-20 16:42:42 Age [y:d:h:m:s]: 03:110:11:55:21
Block: 337648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 854994 RingCT/type: yes/0
Extra: 01cedbcf0daced4e8481c458dc5b36797de551dc3b9c6cd635ca1902df791faf4d02110000000737cb3088000000000000000000

1 output(s) for total of 46.690921706000 dcy

stealth address amount amount idx
00: e137cbdb1a4cd6e860f20f7faa36af6e6dad23e33175581675909962cc79e1a0 46.690921706000 695187 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": 337658, "vin": [ { "gen": { "height": 337648 } } ], "vout": [ { "amount": 46690921706, "target": { "key": "e137cbdb1a4cd6e860f20f7faa36af6e6dad23e33175581675909962cc79e1a0" } } ], "extra": [ 1, 206, 219, 207, 13, 172, 237, 78, 132, 129, 196, 88, 220, 91, 54, 121, 125, 229, 81, 220, 59, 156, 108, 214, 53, 202, 25, 2, 223, 121, 31, 175, 77, 2, 17, 0, 0, 0, 7, 55, 203, 48, 136, 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