Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2648e402fb86d0b7fa6bd4e3f6a2c9aec09d4bd0e3bebf9d87d408266419f33f

Tx prefix hash: d2621584ca32a64f6d11c0ee10ce5626729496e76790b4798b68bc3da1d9c5d4
Tx public key: e37057442db29f78bbe9b12592b373078a90fa3dc635fb21b7c9616c7bf50228
Timestamp: 1694140296 Timestamp [UCT]: 2023-09-08 02:31:36 Age [y:d:h:m:s]: 02:064:03:33:03
Block: 843353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565538 RingCT/type: yes/0
Extra: 01e37057442db29f78bbe9b12592b373078a90fa3dc635fb21b7c9616c7bf502280211000000074b8f5122000000000000000000

1 output(s) for total of 0.985420255000 dcy

stealth address amount amount idx
00: cde53365bbb623a2a27f7201ca9c50cb4f08cb7a548c587f76eeddb9cc4f3bf7 0.985420255000 1296573 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": 843363, "vin": [ { "gen": { "height": 843353 } } ], "vout": [ { "amount": 985420255, "target": { "key": "cde53365bbb623a2a27f7201ca9c50cb4f08cb7a548c587f76eeddb9cc4f3bf7" } } ], "extra": [ 1, 227, 112, 87, 68, 45, 178, 159, 120, 187, 233, 177, 37, 146, 179, 115, 7, 138, 144, 250, 61, 198, 53, 251, 33, 183, 201, 97, 108, 123, 245, 2, 40, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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