Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f5f92c871b8957d9cc3565cbd8fda60afbef694f3c54bc20924bc2171986437

Tx prefix hash: 50e421da81c28ef3ee7fd4eedeeab6cabcc98e6e41ba8b2cd5f4b3f9fb37b0c3
Tx public key: c536853a4d7a847395b60f30c9743f03f34a4de6f93f7168a1f0b35a5442ad36
Timestamp: 1727811277 Timestamp [UCT]: 2024-10-01 19:34:37 Age [y:d:h:m:s]: 00:080:19:12:09
Block: 1122322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57782 RingCT/type: yes/0
Extra: 01c536853a4d7a847395b60f30c9743f03f34a4de6f93f7168a1f0b35a5442ad36021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9adc660aee15da8b497eaa3e953e8eba6edb19b68b9aa1f201f14d46afa5a977 0.600000000000 1604741 of 15

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": 1122332, "vin": [ { "gen": { "height": 1122322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9adc660aee15da8b497eaa3e953e8eba6edb19b68b9aa1f201f14d46afa5a977" } } ], "extra": [ 1, 197, 54, 133, 58, 77, 122, 132, 115, 149, 182, 15, 48, 201, 116, 63, 3, 243, 74, 77, 230, 249, 63, 113, 104, 161, 240, 179, 90, 84, 66, 173, 54, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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