Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 509688e40f6c81ddc77fe0cb7378d0d4de688075e5bd33deceb0134a4545593c

Tx prefix hash: 15a17c168b0cff112090d262afe4d02992009ea28499f4a0e42c04f8d92990f2
Tx public key: 14f82fc85460a20b926d07a541ecddd6df432a16a6d796813fb13f3124e93c79
Timestamp: 1695482224 Timestamp [UCT]: 2023-09-23 15:17:04 Age [y:d:h:m:s]: 01:197:02:08:41
Block: 854488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401916 RingCT/type: yes/0
Extra: 0114f82fc85460a20b926d07a541ecddd6df432a16a6d796813fb13f3124e93c790211000000064b8f5122000000000000000000

1 output(s) for total of 0.905162579000 dcy

stealth address amount amount idx
00: 199918102b566fbb21fa74cd40d71f7877c46ca21ff6824404096b95a1b84c88 0.905162579000 1308464 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": 854498, "vin": [ { "gen": { "height": 854488 } } ], "vout": [ { "amount": 905162579, "target": { "key": "199918102b566fbb21fa74cd40d71f7877c46ca21ff6824404096b95a1b84c88" } } ], "extra": [ 1, 20, 248, 47, 200, 84, 96, 162, 11, 146, 109, 7, 165, 65, 236, 221, 214, 223, 67, 42, 22, 166, 215, 150, 129, 63, 177, 63, 49, 36, 233, 60, 121, 2, 17, 0, 0, 0, 6, 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