Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e1cf8c23bc57b172dfae7492019ee8b2f9347ab8f4e4a509d417b2b48f26b35

Tx prefix hash: 867a38ca2bf4edcec34facda937404a91ad0458b7c13d54953f6105e02fb94b6
Tx public key: e4c69a0f03783c1d88a9e76f75b27b91bd72e7c0af0666fd6c00cbce9436fb64
Timestamp: 1581249025 Timestamp [UCT]: 2020-02-09 11:50:25 Age [y:d:h:m:s]: 04:327:12:19:51
Block: 61314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126182 RingCT/type: yes/0
Extra: 01e4c69a0f03783c1d88a9e76f75b27b91bd72e7c0af0666fd6c00cbce9436fb640211000001c5c71d3ff9000000000000000000

1 output(s) for total of 384.451962127000 dcy

stealth address amount amount idx
00: 3c53c21488a3b8ed42ba685f59614f1af177406cdae15ea3505e71064e681fa4 384.451962127000 112985 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": 61324, "vin": [ { "gen": { "height": 61314 } } ], "vout": [ { "amount": 384451962127, "target": { "key": "3c53c21488a3b8ed42ba685f59614f1af177406cdae15ea3505e71064e681fa4" } } ], "extra": [ 1, 228, 198, 154, 15, 3, 120, 60, 29, 136, 169, 231, 111, 117, 178, 123, 145, 189, 114, 231, 192, 175, 6, 102, 253, 108, 0, 203, 206, 148, 54, 251, 100, 2, 17, 0, 0, 1, 197, 199, 29, 63, 249, 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