Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9050c719fd270ae59af9cfee961d6edc9e83f5ab5ac466d6e3e4db2fc1b79abc

Tx prefix hash: c7b75b8f597530c4c147cfee1dc8759750a928a77c69e9ee10bbdef25649dc83
Tx public key: f14360aacab6907831b3a44a0648bad2edc44162d4d42079e5e97f8066880958
Timestamp: 1577738398 Timestamp [UCT]: 2019-12-30 20:39:58 Age [y:d:h:m:s]: 04:323:22:29:24
Block: 35313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120565 RingCT/type: yes/0
Extra: 01f14360aacab6907831b3a44a0648bad2edc44162d4d42079e5e97f8066880958021100000080c3a1a09f000000000000000000

1 output(s) for total of 468.854929661000 dcy

stealth address amount amount idx
00: 217acb4c0f71584f0eb61c6c76af3ef23ec2dbf1ced49f2a456613db316b18ee 468.854929661000 59477 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": 35323, "vin": [ { "gen": { "height": 35313 } } ], "vout": [ { "amount": 468854929661, "target": { "key": "217acb4c0f71584f0eb61c6c76af3ef23ec2dbf1ced49f2a456613db316b18ee" } } ], "extra": [ 1, 241, 67, 96, 170, 202, 182, 144, 120, 49, 179, 164, 74, 6, 72, 186, 210, 237, 196, 65, 98, 212, 212, 32, 121, 229, 233, 127, 128, 102, 136, 9, 88, 2, 17, 0, 0, 0, 128, 195, 161, 160, 159, 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