Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d58c579ce51e1ecfc13f2caf58eb578d2867824c036859e0388823bf825e07e9

Tx prefix hash: 109e163f6a7105624f605ff54ccc5b68e68f0fc4a3e27b6efa19c0a42beac264
Tx public key: 3ccf5c75b7c8f8a96d5c7cb678ac4610a60f82fb7241e3f9e7bf5cdfed140aed
Timestamp: 1646557149 Timestamp [UCT]: 2022-03-06 08:59:09 Age [y:d:h:m:s]: 02:309:01:28:11
Block: 452444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 740375 RingCT/type: yes/0
Extra: 013ccf5c75b7c8f8a96d5c7cb678ac4610a60f82fb7241e3f9e7bf5cdfed140aed02110000000b2e6b1fd5000000000000000000

1 output(s) for total of 19.447576331000 dcy

stealth address amount amount idx
00: a0d3d5cd36a5249ac14e052ed3b46b9e69fc12cd84c242ba4d90c9365228a873 19.447576331000 867759 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": 452454, "vin": [ { "gen": { "height": 452444 } } ], "vout": [ { "amount": 19447576331, "target": { "key": "a0d3d5cd36a5249ac14e052ed3b46b9e69fc12cd84c242ba4d90c9365228a873" } } ], "extra": [ 1, 60, 207, 92, 117, 183, 200, 248, 169, 109, 92, 124, 182, 120, 172, 70, 16, 166, 15, 130, 251, 114, 65, 227, 249, 231, 191, 92, 223, 237, 20, 10, 237, 2, 17, 0, 0, 0, 11, 46, 107, 31, 213, 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