Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16351d4ce7d7ce19b04ea2debb8c46fab972ff7f8909e7d89e1dc7e554b07b71

Tx prefix hash: 9ca6787827e59e98debed002126bb25251aec89a92574ea356000ea743955a15
Tx public key: 8f4a0cc744d222311fb60016ca08094abf0a02f844e5635c3f92c78ce51c958e
Timestamp: 1587142621 Timestamp [UCT]: 2020-04-17 16:57:01 Age [y:d:h:m:s]: 04:321:12:31:00
Block: 93444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138292 RingCT/type: yes/0
Extra: 018f4a0cc744d222311fb60016ca08094abf0a02f844e5635c3f92c78ce51c958e0211000000eb45705818000000000000000000

1 output(s) for total of 300.872162870000 dcy

stealth address amount amount idx
00: b3510be53fc4eff8aa228c371aa19b18239a2f7e3124aec02d2098e305b29e6c 300.872162870000 166450 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": 93454, "vin": [ { "gen": { "height": 93444 } } ], "vout": [ { "amount": 300872162870, "target": { "key": "b3510be53fc4eff8aa228c371aa19b18239a2f7e3124aec02d2098e305b29e6c" } } ], "extra": [ 1, 143, 74, 12, 199, 68, 210, 34, 49, 31, 182, 0, 22, 202, 8, 9, 74, 191, 10, 2, 248, 68, 229, 99, 92, 63, 146, 199, 140, 229, 28, 149, 142, 2, 17, 0, 0, 0, 235, 69, 112, 88, 24, 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