Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f16d6cc82631c9d45569fae09ed24a4e97f8395325dabe11b62cea54f66985c

Tx prefix hash: aa78e5f3a5346fd6b60e8a5e2ccc987109bd8acffa8489c8d2b6f2028aaa5ae1
Tx public key: b678d7ea9d568ea1aa0189238a3ecdc214f66cd7e766bfa1d765fd6e2ee584bd
Timestamp: 1676570577 Timestamp [UCT]: 2023-02-16 18:02:57 Age [y:d:h:m:s]: 01:282:13:18:12
Block: 698388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462860 RingCT/type: yes/0
Extra: 01b678d7ea9d568ea1aa0189238a3ecdc214f66cd7e766bfa1d765fd6e2ee584bd02110000000174b6d784000000000000000000

1 output(s) for total of 2.978177354000 dcy

stealth address amount amount idx
00: aea352d27cb28e2dcecad90096dfb58e7551a46ab6d133440b460b432f08b0b6 2.978177354000 1141685 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": 698398, "vin": [ { "gen": { "height": 698388 } } ], "vout": [ { "amount": 2978177354, "target": { "key": "aea352d27cb28e2dcecad90096dfb58e7551a46ab6d133440b460b432f08b0b6" } } ], "extra": [ 1, 182, 120, 215, 234, 157, 86, 142, 161, 170, 1, 137, 35, 138, 62, 205, 194, 20, 246, 108, 215, 231, 102, 191, 161, 215, 101, 253, 110, 46, 229, 132, 189, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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