Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6f5ab98bc2c289e1dc3d689e57610efd070990d4abc2f09dd4674b012d3bd25

Tx prefix hash: cc7a37b9c09e62bb07cb03fc075cb61230eba88a332c2b51b2c0ef64d4fd0807
Tx public key: 815fbcc6713d5efd812c1dea20d98d070d84f40e932a843f45b5bb8256265acd
Timestamp: 1660684579 Timestamp [UCT]: 2022-08-16 21:16:19 Age [y:d:h:m:s]: 02:092:08:13:23
Block: 567360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587399 RingCT/type: yes/0
Extra: 01815fbcc6713d5efd812c1dea20d98d070d84f40e932a843f45b5bb8256265acd02110000000d33af99f4000000000000000000

1 output(s) for total of 8.092839073000 dcy

stealth address amount amount idx
00: c36dbfd2914d6d1d4e9f9c46123510a2b87c5826837442c9d7dbbef0bbcc1ff7 8.092839073000 1000461 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": 567370, "vin": [ { "gen": { "height": 567360 } } ], "vout": [ { "amount": 8092839073, "target": { "key": "c36dbfd2914d6d1d4e9f9c46123510a2b87c5826837442c9d7dbbef0bbcc1ff7" } } ], "extra": [ 1, 129, 95, 188, 198, 113, 61, 94, 253, 129, 44, 29, 234, 32, 217, 141, 7, 13, 132, 244, 14, 147, 42, 132, 63, 69, 181, 187, 130, 86, 38, 90, 205, 2, 17, 0, 0, 0, 13, 51, 175, 153, 244, 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